Conversation
|
REQUEST FOR PRODUCTION RELEASES: This will add The following labels are available |
|
Ciao @jackal1-66 I saw that the generation is quite demanding, I would increase the number of events without restricting the CPU. What do you think? |
|
Ciao @njacazio , theoretically I have no issue with this PR, however this file should be used for the LF production requested by Giuseppe https://its.cern.ch/jira/browse/O2-6220. Are you in touch with him and have agreed to change the number of freeze-out events? Is there a strong reason to change the freeze-out events? It would be interesting to check the CPU time difference between the two configurations. |
|
Ciao @jackal1-66 I see, good point. Let's do another file then. The CPU usage is about the same but the number of events is x10. |
njacazio
changed the title
|
Ciao Niccolo' sorry I think I explained myself badly. You need to delete the test file you created and simply add at the top of the ini file you're adding the string |
| @@ -0,0 +1,11 @@ | |||
| [GeneratorExternal] | |||
There was a problem hiding this comment.
Can you please add:
#---> GeneratorEPOS4
this will redirect the generator test to a pre-existing one
| eos x3ff !eos activated (epos standard EoS) | ||
| hacas full !hadronic cascade activated (UrQMD) | ||
| set nfreeze 10 !number of freeze out events per hydro event | ||
| set nfreeze 1 !number of freeze out events per hydro event |
There was a problem hiding this comment.
delete space and add tab? Just so that the file is not considered in the diff (cleaner way)
|
Ciao @jackal1-66 do you get the error? Is it legit? |
|
Ciao Nicolo' I will run some local tests |
|
The issue is localised in the CI test. There might be a problem simply with EPOS4, I need to debug this further, however I tested EPOS4 both in a docker and in my local installation. Your configuration is literally the same as the usual validated one. So I will merge this and take note to look into the CI failure. |
2 participants
No description provided.